| Author |
Thread Statistics | Show CCP posts - 6 post(s) |
|
CCP FoxFour
C C P
C C P Alliance
3812
   |
Posted - 2015.01.09 14:19:27 -
[1] - Quote
Simple yet hopefully useful. :D
@CCP_FoxFour // Technical Designer // Team Size Matters
Third-party developer? Check out the official developers site for dev blogs, resources, and more.
|
|
|
CCP FoxFour
C C P
C C P Alliance
3815
|
Posted - 2015.01.09 18:23:54 -
[2] - Quote
Max Kolonko wrote:and will we be able now to use:
url_to_sell_orders?type=type_id,
instead of
url_to_sell_orders?type=url_to_type
???
No, not yet.
@CCP_FoxFour // Technical Designer // Team Size Matters
Third-party developer? Check out the official developers site for dev blogs, resources, and more.
|
|
|
CCP FoxFour
C C P
C C P Alliance
3815
|
Posted - 2015.01.09 20:52:43 -
[3] - Quote
Cadiz Aragon wrote:cool!. Is making a method available to access this data without having to go through SSO url redirection still in the works?
Not for these market resources.
@CCP_FoxFour // Technical Designer // Team Size Matters
Third-party developer? Check out the official developers site for dev blogs, resources, and more.
|
|
|
CCP FoxFour
C C P
C C P Alliance
3835
|
Posted - 2015.01.19 10:20:00 -
[4] - Quote
brammator wrote:1. It's not on TQ now, right?
2. Is this endpoint listed at root folder? Can't find it in crest-public and api-sisi lists.
3. Do you plan to implement /market/regionID/orders/buy/typeID/ instead of mixing path and parameter elements? Or this is some good scheme I don't understand yet?
4. Is there working oauth/verify endpoint on public-crest.eveonline.com and api-sisi.testeveonline.com, or I should stick to login.eveonline.com and sisilogin.testeveonline.com?
EDIT.
5. Could you add info about required scope to root list of endpoints?
- Yes the changes on on TQ now.
- The market endpoint? You get it by going through the regions. See more about that here: https://developers.eveonline.com/blog/article/nom-nom-tastey-market-data
- No as that breaks the RESTful nature of the API.
- You should be using crest-tq.eveonline.com
- That will be in the auto generated documentation that I hope to get out next month.
@CCP_FoxFour // Technical Designer // Team Size Matters
Third-party developer? Check out the official developers site for dev blogs, resources, and more.
|
|
|
CCP FoxFour
C C P
C C P Alliance
3836
|
Posted - 2015.01.19 18:46:25 -
[5] - Quote
brammator wrote:Thanks for answers. However, you see, to develop or use third-party api library, I need this endpoint to be declared in some sort of list. Or just hardcode it as "crest.MarketEndpoint.region[1000000002].orders.buy(type = crest.href(587))" I'd prefer first way. What is the point of having bunch of not-working-yet endpoints listed at root, but not having working and very demanded one?
Third party libraries should always follow links. You shouldn't need to know the route for things. People who use the library should know they go from the root v3 to regions v1 to market v1. That or the client should be built from the auto generated documentation that is not out yet.
The SSO links should be included in the root of the API, https://crest-tq.eveonline.com/
See: "authEndpoint": {"href": "https://login-tq.eveonline.com/oauth/token/"}
brammator wrote:CCP FoxFour wrote: (brammator)5. Could you add info about required scope to root list of endpoints?
* That will be in the auto generated documentation that I hope to get out next month.
I'd like to see it in root crest list too, for mapping automation.
It will be.
@CCP_FoxFour // Technical Designer // Team Size Matters
Third-party developer? Check out the official developers site for dev blogs, resources, and more.
|
|
| |
|